Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(config): use SUPABASE env prefix #2778

Merged
merged 2 commits into from
Oct 17, 2024
Merged

fix(config): use SUPABASE env prefix #2778

merged 2 commits into from
Oct 17, 2024

Conversation

avallete
Copy link
Contributor

What kind of change does this PR introduce?

Bug fix, feature, docs update, ...

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

@sweatybridge sweatybridge merged commit 5f8587b into develop Oct 17, 2024
11 checks passed
@sweatybridge sweatybridge deleted the fix/use-supabase-env-prefix branch October 17, 2024 18:52
@coveralls
Copy link

Pull Request Test Coverage Report for Build 11391151652

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 5 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.03%) to 59.748%
Files with Coverage Reduction New Missed Lines %
internal/gen/keys/keys.go 5 12.9%
Totals Coverage Status
Change from base Build 11390922765: -0.03%
Covered Lines: 6356
Relevant Lines: 10638
💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sweatybridge sweatybridge sweatybridge approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@avallete @coveralls @sweatybridge